Flexible telematics system and method for providing telematics to a vehicle

ABSTRACT

A method for providing telematics to a vehicle includes the steps of communicatively connecting a user-removable telematics component to an integrated communication device of the vehicle, the integrated communication device having a memory holding a list uniquely identifying at least one mobile communication device selected from a currently paired mobile communication device, a previously paired mobile communication device, and a pre-defined mobile communication device, transmitting a request for information out from the telematics component utilizing a communications path between the data pump and the integrated communication device, receiving the request for information at an off-site telematics information provider, and channeling a response to the request for information from the off-site telematics information provider automatically through the mobile communication device.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the priority, under 35 U.S.C. §119, of U.S. Provisional Patent Application Ser. No. 61/024,956, filed Jan. 31, 2008, the entire disclosure of which is hereby incorporated herein by reference in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

n/a

FIELD OF THE INVENTION

The present invention relates generally to providing a telematics system in a vehicle that has not previously been set up for such a system. More specifically, the present invention relates to a simplified telematics system for use in a new vehicle at a manufacturing site, or as a retrofitted telematics system to an existing vehicle, and methods for providing such telematics to a vehicle.

BACKGROUND OF THE INVENTION

As consumer vehicles, such as cars and trucks, become more technologically complicated, operation of that vehicle becomes even more difficult. Today there is such an array of devices in trucks and cars that driver distraction is a major problem. To ease the driver's burden, mobile telematics systems and services have evolved that integrate wireless communications and (usually) location determining devices into vehicles to perform a number of tasks including, for example, carrying out remote engine diagnostics, locating stolen vehicles, and providing roadside assistance. Integration of such telematics systems requires significant design and implementation costs, not to mention the costly hardware that needs to be installed in the vehicle. Even though some manufacturers have started to include telematics systems with new vehicles, most new vehicles on the road today do not have such systems. More importantly, most manufacturers do not design vehicles to house such complex technology. When the manufacturers do incorporate this technology, it requires extra wiring and complexity. Thus, a need exists to make simpler systems both for installation at the site of manufacturing and retrofitting into existing vehicles without having to modify the vehicle in any substantial way (whether in terms of cost or labor).

While most vehicles do not have telematics systems pre-installed, many vehicles do have other kinds of integrated electronic communication devices. One kind of communications device that can be found in some vehicles is a Bluetooth transceiver. Bluetooth is an industrial specification for wireless personal area networks (PANs). A Bluetooth gateway provides measures for connection and exchanging information between devices such as mobile phones, laptops, PCs, printers, digital cameras, and video game consoles over a secure, globally unlicensed short-range radio frequency. Equipping vehicles with a Bluetooth transceiver (also referred to as a Bluetooth gateway) makes it possible to link the vehicle with other Bluetooth-compatible devices brought into or near the car, the most common of which is a Bluetooth-compatible cell phone.

When a Bluetooth-compatible cell phone is brought into a vehicle equipped with a Bluetooth transceiver, a data link is created between the phone and the transceiver. The most common feature made available to owners of vehicles so equipped is the ability to talk on the cell phone in a hands-free manner. In this embodiment, the vehicle is provided with a microphone (at least one near or directed at the head of the driver) for receiving audio from at least the driver (and, possibly, any passenger within the vehicle). A speaker system commonly associated with a vehicle's radio is temporarily connected to the transceiver and is, thereby, used to present any received audio signals to the user. Of course, dedicated speakers can be provided in the vehicle for this function or even a combination of these exemplary configurations. With such a configuration, bi-directional audio communication is made available to occupants of the vehicle.

Another common Bluetooth feature is the ability to display and/or use the phone list stored in the cell phone for making calls without having to touch the cell phone. Either the vehicle is provided with a voice-recognition system to select a particular number in the cell phone's phone number list or has mechanical controls for doing so, or both. Such systems, however, do not have the ability to expand beyond these limited functions.

There exists a need to be able to provide a simplified, cost-effective telematics system to be used both by original equipment manufacturers for new vehicle installations and by owners of existing vehicles for retrofitting into vehicles only having a Bluetooth transceiver without having to modify the vehicle in any substantial way (whether in terms of cost or labor). Even with the advent of telematics systems in vehicles today, there is not currently a service that is deployed to solve the above-described problems. Thus, it would be a significant advancement in the art to provide a telematics system in a vehicle where one did not exist before and where the vehicle was not pre-configured to provide such features.

SUMMARY OF THE INVENTION

Briefly, in accordance with the present invention, disclosed is a device and method for simplifying manufacturer-fitted telematics systems and retrofitting a telematics communication and control unit in a vehicle configured with a Bluetooth transceiver. This system and its process makes use of existing, in-vehicle Bluetooth gateways (in one embodiment, referred to as a “Sync Box”) by adding a component that contains all needed additional hardware for carrying out the desired telematics functions, for example, a positioning module (e.g., GPS) and a data module. The data module can be a phone with voice capability, but it can also be merely a data modem. Software is also added. Each vehicle equipped with Bluetooth communications capabilities has a Bluetooth gateway with particular characteristics, which can be obtained from the vehicle's manufacturer. A vehicle-specific software application is added to the Bluetooth gateway. In this way, the inventive telematics component (also referred to as a telematics gateway) can be linked to user interfaces of the vehicle through the Bluetooth gateway. This link is achieved through the standard Bluetooth PAN. This software application contains appropriate logic for activation of the telematics component.

While it is known to use vehicle interfaces to receive and transmit audio phone calls through a vehicle's Bluetooth gateway, this gateway has not been used with data-oriented telematics functions. Where, for example, the phone does not have service available for communicating audio phone calls, the present invention still allows telematics functionality in a vehicle through use of the inventive data-oriented communication system. Moreover, the present invention provides this functionality as a retro-fitting system. Thus, the present invention permits, for the first time, telematics functionality in a vehicle without requiring the vehicle manufacturer to pre-design and pre-install such functionality.

In prior-art vehicle telematics components, a dedicated bi-directional voice communications link was required. This link was provided by including an integrated device containing the same functionality as a standard cellular phone. Concomitantly, charges for this link were incurred and were at a level comparable to a consumer's pre-existing portable cell phone. Such systems, therefore, caused the consumer to pay approximately double fees for these two cellular devices.

In contrast, the present invention entirely eliminates the need for a bi-directional, voice-supporting cellular device to be included in the telematics component. Instead, the telematics component of the present invention needs only to have a data transceiver, also referred to as a data pump. The telematics component can carry out all external data communication through this data pump. More specifically, when a user enters a vehicle with a Bluetooth-compatible device, the Bluetooth system sets up a communications link between the system and the device. This device can be already recognized (where it has been coupled with this system in the past) or it can be new to the system (in which case, a recognition protocol between the system and the device is carried out). The Bluetooth system stores information about each such device in a client stack, in which each such device is uniquely identified and recorded. The Bluetooth system is, then, able to direct data to, from, and through each such device in parallel or by multiplexing. The telematics component of the present invention utilizes this information and connection to communicate outside the vehicle for voice. For example, if a request for information is transmitted out from the telematics component, the path for such a communication will be between the data pump and the Bluetooth system, which data pump is capable of sending out the query data and receiving back the answer data. By knowing which devices are paired, the telematics component can embed the unique calling identifier (e.g., the cellular phone number) within the transmitted data. Then, when the off-site telematics information provider responds to the query, the response is channeled automatically through the paired device. The transaction can be entirely non-voice, in which the user is entirely unaware that their data pump was used for this telematics request, or can include (partially or wholly) voice data. In the latter case, the user's phone will ring, just as receiving a phone call, and the voice response from the telematics operator (whether automated, recorded or live) is conveyed to the vehicle user. In an alternative exemplary embodiment, the telematics component does not embed the unique calling identifier and calls a particular pre-programmed cell phone that is set by the system or the user to receive a call when a given event occurs.

If there is a reason to originate data from a telematics operator to the vehicle or an occupant of the vehicle, the data is sent through the data pump. Then, when a mobile terminated communication occurs (i.e., to the vehicle), each of these paired devices is polled to determine if they are currently paired with the telematics component. When such a query returns a positive result, the data can be communicated (e.g., displayed) to the current user through one of the currently paired devices.

Thus, the present invention entirely eliminates the need for a voice-capable cellular device to be included with the telematics component. By utilizing the vehicle's Bluetooth gateway, the present invention can take hold, temporarily, of the consumer's portable cell phone to carry out the needed telematics voice communication, resulting in a significant cost savings.

The invention provides a simplified manufacturer's install or retrofitting telematics system and method for providing telematics to a vehicle that overcome the hereinafore-mentioned disadvantages of the heretofore-known devices and methods of this general type and that provides a telematics system in a vehicle that has not previously been set up for such a system.

With the foregoing and other objects in view, there is provided, in accordance with the invention, a method for providing telematics to a vehicle, including the steps of communicatively connecting a user-removable telematics component to an integrated communication device of the vehicle, the integrated communication device having a memory holding a list uniquely identifying at least one mobile communication device selected from a currently paired mobile communication device, a previously paired mobile communication device, and a pre-defined mobile communication device, transmitting a request for information out from the telematics component utilizing a communications path between the data pump and the integrated communication device, receiving the request for information at an off-site telematics information provider, and channeling a response to the request for information from the off-site telematics information provider automatically through the mobile communication device.

In accordance with another mode of the invention, data is originated from the off-site telematics information provider to the vehicle and the data is sent to the vehicle through the data pump.

In accordance with a further mode of the invention, each device paired with the integrated communication device is polled to determine if they are currently paired with the telematics component and, after receiving an affirmative poll from at least one of the devices paired with the integrated communication device, the data is communicated from the data pump through one currently paired device to the current user of the one currently paired device.

In accordance with an added mode of the invention, the communicative connection of the telematics component to the integrated communication device is wireless.

In accordance with an additional mode of the invention, the connection step is carried out by communicatively connecting the telematics component to an integrated Bluetooth communication device of the vehicle, the Bluetooth communication device having a memory holding a list uniquely identifying at least one mobile Bluetooth communication device selected from a currently paired mobile Bluetooth communication device, a previously paired mobile Bluetooth communication device, and a pre-defined mobile Bluetooth communication device, the transmitting step is carried out by transmitting a request for information out from the telematics component utilizing a communications path between the data pump and the integrated Bluetooth communication device, and the channeling step is carried out by channeling a response to the request for information from the off-site telematics information provider automatically through the mobile Bluetooth communication device.

In accordance with yet another mode of the invention, the transmission and the received response are carried out entirely without voice data. Alternatively, the transmission and the received response are carried out entirely with voice data. Alternatively, the transmission and the received response are carried out with both voice and non-voice data.

In accordance with yet a further mode of the invention, the paired device is a vehicle occupant's cell phone and the channeling step is carried out through the cell phone.

In accordance with yet an added mode of the invention, there is provided the step of embedding within the request for information at least one unique calling identifier of the mobile communication device with the telematics component.

In accordance with yet an additional mode of the invention, the mobile communication device is a currently paired cell phone of an occupant of the vehicle and which further comprises embedding within the request for information the unique calling identifier of the cell phone with the telematics component.

In accordance with again another mode of the invention, there is provided the step of embedding within the request for information at least one unique calling identifier of the mobile communication device with the telematics component.

In accordance with a concomitant mode of the invention, the channeling step is carried out automatically through a given cell phone selected prior to transmitting the request for information.

Although the invention is illustrated and described herein as embodied in a simplified manufacturer's install or retrofitting telematics system and method for providing telematics to a vehicle, it is, nevertheless, not intended to be limited to the details shown because various modifications and structural changes may be made therein without departing from the spirit of the invention and within the scope and range of equivalents of the claims. Additionally, well-known elements of exemplary embodiments of the invention will not be described in detail or will be omitted so as not to obscure the relevant details of the invention.

Other features that are considered as characteristic for the invention are set forth in the appended claims. As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention, which can be embodied in various forms. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one of ordinary skill in the art to variously employ the present invention in virtually any appropriately detailed structure. Further, the terms and phrases used herein are not intended to be limiting; but rather, to provide an understandable description of the invention. While the specification concludes with claims defining the features of the invention that are regarded as novel, it is believed that the invention will be better understood from a consideration of the following description in conjunction with the drawing figures, in which like reference numerals are carried forward. The figures of the drawings are not drawn to scale.

Before the present invention is disclosed and described, it is to be understood that the terminology used herein is for describing particular embodiments only and is not intended to be limiting. The terms “a” or “an”, as used herein, are defined as one or more than one. The term “plurality,” as used herein, is defined as two or more than two. The term “another,” as used herein, is defined as at least a second or more. The terms “including” and/or “having,” as used herein, are defined as comprising (i.e., open language). The term “coupled,” as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. As used herein, the term “about” or “approximately” applies to all numeric values, whether or not explicitly indicated. These terms generally refer to a range of numbers that one of skill in the art would consider equivalent to the recited values (i.e., having the same function or result). In many instances these terms may include numbers that are rounded to the nearest significant figure.

The terms “program,” “software application,” and the like as used herein, are defined as a sequence of instructions designed for execution on a computer system. A “program,” “computer program,” or “software application” may include a subroutine, a function, a procedure, an object method, an object implementation, an executable application, an applet, a servlet, a source code, an object code, a shared library/dynamic load library and/or other sequence of instructions designed for execution on a computer system.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, the invention will be described in more detail by exemplary embodiments and the corresponding figures. By schematic illustrations that are not true to scale, the figures show different exemplary embodiments of the invention.

FIG. 1 is a diagrammatic illustration of a telematics component and base station according to the invention associated with a prior art vehicle and a cell phone in that vehicle;

FIG. 2 is a diagrammatic illustration of a process for utilizing the telematics component according to an exemplary embodiment of the invention;

FIG. 3 is a flow chart of the process for utilizing the telematics component of FIG. 2; and

FIG. 4 is a diagrammatic illustration of a process for utilizing the telematics component according to an exemplary embodiment of the invention.

DETAILED DESCRIPTION

Herein various embodiment of the present invention are described. In many of the different embodiments, features are similar. Therefore, to avoid redundancy, repetitive description of these similar features may not be made in some circumstances. It shall be understood, however, that description of a first-appearing feature applies to the later described similar feature and each respective description, therefore, is to be incorporated therein without such repetition.

FIG. 1 shows a diagrammatic illustration of an exemplary telematics component 10 according to the invention. In this embodiment, the telematics component 10 includes a Global Positioning System (GPS) device 11, a data pump 12, and a Bluetooth transceiver 13. Each of these sub-systems is connected to a central controller 14, which can be a central processing unit (CPU), such as a microprocessor. Other telematics sub-systems can also be included in the telematics component 10 as desired. The telematics component 10 is installed (arrow A) in a vehicle 20 having a gateway 21 containing a Bluetooth transceiver 22. Power can be supplied to the component 10 either through a self-contained battery pack or a hard-wired connection to a power supply of the vehicle (e.g., the battery).

The GPS device 11 is self-contained and, with the CPU 14 and appropriate internal software, is able to output any desired GPS data (e.g., time or position in various units or formats). The data pump 12 is configured to receive and supply data to the Bluetooth transceiver 13 for processing by the gateway 21 or CPU 14. Such data will be addressed in further detail below. The Bluetooth transceiver 13 is configured as a standard Bluetooth interface so that the telematics component 10 is recognized and paired just like any other device after the appropriate acknowledgement routine is carried out. Alternatively, the telematics component 10 can be hardwired into the vehicle.

It is noted that each vehicle 20 can have its own kind of gateway 21. Thus, display, control, and all other functions capable of being carried out by the gateway 21 will most likely be device-specific. Accordingly, the telematics component 10 is configured with appropriate software 15 for interfacing with each of the different gateways 21 presented for connection. In one embodiment, the telematics component 10 can be configured to operate with a single, specific gateway 21. Thus, different telematics components 10 a-n are created, one for each of the possible gateways 21. In such a case, the vehicle 20 in which the component 10 a-n is to be installed is identified and the appropriate component 10 a-n is used. Alternatively, the component 10 can be configured with all possible gateway interface operating configurations and, upon installation can be programmed to execute the appropriate configuration for that specific gateway 21. This execution can be manual (based upon user input of the corresponding vehicle identification) or can be automatic (through a sequence of question and answer transmissions to the gateway 21). Specifications of each gateway 21 may be provided by the vehicle manufacture so that the software 15 can be developed accordingly.

The customized software 15 enables a single GPS system 11, a single data system 12, and a single Bluetooth system 13 to be customized for interfacing with any functionality operable by or through the vehicle's gateway 21. Thus, even if the vehicle was not designed to provide GPS functionality, as long as the gateway 21 has a display (or is connected to a display) and as long as that display's specifications have been provided beforehand, the software 15 can format the call status/progress updates into a form suitable for projection by the existing display to the user.

As set forth above, standard gateways 21 have the ability to interface with cell phones 30 that are present in or near the vehicle 20. Communication can occur from the vehicle 20 through the cell phone 30 to a third party or from a third party to the cell phone 30 (e.g., SMS text) or through the cell phone 30 to the occupant in the vehicle 20 (e.g., voice call). The telematics component 10 is able to expand upon this ability to bi-directionally communicate outside the vehicle 20 by linking to the cell phone 30 through the gateway 21. Because the telematics component 10 has the ability to communicate any data it desires over the Bluetooth transmission channel 40 (i.e., the Bluetooth gateway), it can, for example, obtain the current paired client list of the Bluetooth 22 device in the gateway 21, and use one (or more) of the paired devices remotely through the secondary Bluetooth transmission channel 50. More specifically, if the telematics component 10 needed to send a message to a base station 60, then the data pump 12 would configure the appropriate data to be transmitted along with relevant control logic. Once the data pump 12 acknowledged that the communications channel 71 to the base station 60 was open (which state the telematics component 10 could detect), the control logic would then cause the appropriate data to be transmitted to the base station 60. The present invention, therefore, entirely eliminates the need for a bi-directional, voice-supporting cellular device to be included in the telematics component 10.

There are a number of exemplary uses for the telematics component 10 so configured. One exemplary use is the most commonly found use of a telematics device—to summon roadside assistance. For the present example, the entity supplying the telematics component 10 has live operators at a remote facility, e.g., at the base station 60, for providing roadside assistance through a voice communication. Further, the telematics component 10 has a user interface control (which is not illustrated in FIG. 1 but could include software on gateway 21) that calls the operator center upon a single actuation. For example, the telematics component 10 can have a red “emergency” button that, when pressed, opens a communications channel to the operator. Accordingly, when the vehicle occupant presses the button, the appropriate software 15 is called up to enable a “live-operator-communication.” The software 15 communicates via Bluetooth 13 to Bluetooth 22 to receive the active paired phones list. The active paired phones list is then passed to the data pump 12. Whatever additional data is needed for this operation (e.g., the destination address for the data center at the base station 60) is used by the data pump 12. The data pump 12 then triggers the gateway 21, which requires a first paired device (i.e., the cell phone 30) to receive a phone call from the base station 60, thus, carrying out the desired “live-operator-communication” function.

If, as shown in FIG. 1, the telematics component 10 has an embedded GPS system 11, the data sent to the base station 60 can include current GPS location coordinates. In this way, the operator could be provided with the information pinpointing the vehicle's location before voice communication occurs between the operator and the occupant.

Beneficial to the inventive system and process is the ability to utilize any Bluetooth communication device within range of the vehicle 20. Whether or not the device has already been recognized (i.e., coupled with the gateway 21 in the past) or is new to the system (in which case, a recognition protocol between the system and the device may need to be carried out), if the Bluetooth system 22 has the device's identification information in its client stack, then the telematics component 10 has the possibility of directing calls to and through each such device as desired. In normal use, however, the telematics component 10 merely retrieves the identity of all currently paired devices from Bluetooth 22. If desired, the component 10 can periodically communicate this information to the base station 60, which keeps a vehicle-specific paired-device list.

Roadside assistance is only one of the possible telematics functions that could be provided with the inventive telematics component 10 of the present invention. Another function that could be provided with the component 10 is a door-unlock command. If the gateway 21 is communicatively coupled with the device that unlocks a locked door of the vehicle, then the telematics component 10 can interface with the door-unlocking device. As set forth above, the manufacturer provides the specifications for causing the gateway 21 to actuate the door-unlocking device. The telematics controller 10 stores this data internally. After appropriate authentication, the operator can transmit the pre-programmed authorization command to the telematics controller 10 via the data pump 12. When the telematics controller 10 receives the authorization command, the appropriate control logic is sent to the gateway 21 to activate the door-opening device. If the gateway 21 is similarly connected to the vehicle starting assembly, then the telematics controller 10 can effect a remote engine start with little added difficulty. Likewise, if the gateway 21 has access to the vehicle's diagnostics bus, then any available diagnostic status can be made accessible not only to the driver, but also to an operator at the base station 60. In an emergency, where the driver/passenger(s) is not available, the telematics controller 10 can be programmed to automatically send a diagnostics state(s) to the base station 60.

For example and with reference to FIG. 2, after an event occurs that requires the telematics software to take an action, referred to herein as an event call, the base station 60 can be provided automatically with both diagnostics data and GPS position data. Also sent to the base station 60 is the cell phone number for one or more currently paired cell phones 30 within the Bluetooth PAN of the vehicle 20. Upon receiving the event call, an operator can be directed to call any or all of the currently paired cell phones 30 associated with that vehicle 20.

More specifically, reference is made to the flow chart of FIG. 3 to describe this process. Beginning in Step 100, the system waits for an event call. When an event call occurs, an event signal is sent to the gateway 21 in Step 200. The telematics software on the gateway 21 recognizes receipt of the event call. In Step 300, the telematics software notifies the telematics controller 10 and sends the appropriate data to the telematics controller 10 to list at least one cell phone 30 in the Bluetooth stack of the gateway 21. In Step 400, the telematics controller 10 sends an event call signal to the base station 60 and notifies the gateway 21 that the data was sent. The cell phone 30 receives a call from the base station 60 connecting the cell phone audio to the base station 60 in Step 500. If desired, audio from the cell phone 30 can be routed to the vehicle's speakers to the occupant via Bluetooth 22. In this way, by having the base station 60 call the vehicle directly, the inventive system avoids an issue that has plagued the telematics industry since its early days—bad Caller-ID. Additionally, or alternatively, the base station 60 can have a fallback phone number for such an emergency and, simultaneously or thereafter, can require an operator to call that phone number.

Deployment of an airbag and the resulting communication with the invention is described with reference to FIG. 4. After an air bag is deployed, the base station 60 needs to be provided with both diagnostics data and GPS position data. More specifically, an airbag trigger signal is sent to the gateway 21. The telematics software on the gateway 21 recognizes receipt by the gateway 21 of the airbag trigger. The telematics software notifies the telematics controller 10 and sends the appropriate data to the telematics controller 10 send notification to the base station and to list at least one cell phone 30 in the Bluetooth stack of the gateway 21. The telematics controller 10 sends an airbag deployment signal to the base station 60 and notifies the gateway 21 that the data was sent. Also sent to the base station 60 is the cell phone number for one or more currently paired cell phones 30 within the Bluetooth PAN of the vehicle 20. Upon receiving an accident indication, an operator can be directed to call any or all of the currently paired cell phones 30 associated with that vehicle 20. The cell phone 30 receives a call from the base station 60 informing the user of the cell phone of the airbag deployment. If desired, audio from the cell phone 30 can be routed to the vehicle's speakers to the occupant via Bluetooth 22.

There are instances where the driver/owner of the vehicle 20 should be notified about current conditions of the vehicle 20. For example, if the vehicle's alarm system activates and the driver is not within range of the vehicle 20, then the operator at the base station 60 can be silently informed of the alarm's activation and call a pre-programmed cell phone, such as the owner's phone, or can be asked to call the police with GPS position information of the vehicle 20.

Other telematics functions require information from the GPS module 11. If position, direction, and speed are made available to the software 15 and base station 60 from the telematics controller 10, then it is possible to carry out, for example, speed alerts, real-time remote vehicle location requests, geo-fencing, stolen vehicle recovery procedures, and updates for traffic, weather and/or parking. If the in-vehicle display controlled by the gateway 21 is sufficiently robust, then navigation, point-of-interest, and trip-planning features can be made available to the driver without installing a costly navigation system in the vehicle.

A device and method for simplifying manufacturer-fitted telematics systems and retrofitting a telematics communication and control unit in a vehicle configured with a Bluetooth transceiver has been disclosed that overcomes the disadvantages of the prior art. 

What is claimed is:
 1. A method for providing telematics to a vehicle, which comprises: communicatively connecting a user-removable telematics component to an integrated communication device of the vehicle, the integrated communication device having a memory holding a list uniquely identifying at least one mobile communication device, the at least one mobile communication device currently connected or configured to be connected to the integrated communication device through a wireless personal area network communication channel, the integrated communication device being operable to: locally generate the list of the at least one mobile communication device; and update the list to reflect the currently connected at least one mobile communication device; transmitting a request for information out from the telematics component to an off-site telematics information provider utilizing a communications path between a data pump of the telematics component and the off-site telematics information provider; and receiving a channeled response to the request for information from the off-site telematics information provider automatically through the at least one mobile communication device currently connected to the integrated communication device.
 2. The method according to claim 1, which further comprises originating data from the off-site telematics information provider and sending the data to the vehicle through the data pump.
 3. The method according to claim 2, which further comprises polling each device paired with the integrated communication device to determine if they are currently paired with the telematics component and, after receiving an affirmative poll from at least one of the devices paired with the integrated communication device, communicating the data from the data pump through the at least one currently paired device to a current user of the at least one currently paired device.
 4. The method according to claim 1, wherein the communicative connection of the telematics component to the integrated communication device is wireless.
 5. The method according to claim 4, which further comprises: carrying out the connection step by communicatively connecting the telematics component to an integrated Bluetooth communication device of the vehicle, the Bluetooth communication device having the memory holding a list uniquely identifying at least one mobile Bluetooth communication device selected from a currently paired mobile Bluetooth communication device, a previously paired mobile Bluetooth communication device, and a pre-defined mobile Bluetooth communication device; carrying out the transmitting step by transmitting the request for information out from the telematics component utilizing the communications path between the data pump and the integrated Bluetooth communication device; and carrying out the channeling step by channeling the response to the request for information from the off-site telematics information provider automatically through the at least one mobile Bluetooth communication device.
 6. The method according to claim 1, which further comprises wherein the transmission and the received response are carried out entirely without voice data.
 7. The method according to claim 1, which further comprises wherein the transmission and the received response are carried out entirely with voice data.
 8. The method according to claim 1, which further comprises wherein the transmission and the received response are carried out with both voice and non-voice data.
 9. The method according to claim 1, which further comprises wherein the paired device is a vehicle occupant's cell phone and which further comprises carrying out the channeling step through the cell phone.
 10. The method according to claim 1, which further comprises embedding within the request for information at least one unique calling identifier of the at least one mobile communication device with the telematics component.
 11. The method according to claim 1, wherein the at least one mobile communication device is a currently paired cell phone of an occupant of the vehicle and which further comprises embedding within the request for information a unique calling identifier of the cell phone with the telematics component.
 12. The method according to claim 1, which further comprises embedding within the request for information at least one unique calling identifier of the at least one mobile communication device with the telematics component.
 13. The method according to claim 1, which further comprises carrying out the channeling step automatically through a given cell phone selected prior to transmitting the request for information. 